|
Rob Hart
|
|
|
Group: Forum Members
Posts: 77,
Visits: 454
|
A quick addendum.
One chap who had experienced this "the app has stopped working" problem got in touch with us today to let us know that without him knowingly doing anything to his device, suddenly SkyDemon is now working normally. This is rather bizarre.
At this point we still cant really be sure what has happened here, but I would ask any guys who have seen this issue and suddenly found that it works fine, to try to note if any automatic updates of any apps (or the operating system itself) might have occurred in the interim; we would be extremely interested to hear about any such instances!
|
|
|
|
|
Rob Hart
|
|
|
Group: Forum Members
Posts: 77,
Visits: 454
|
Afternoon everyone,
I have been looking into this whenever I have been able to get a few minutes, but so far I haven't been able to come to any firm conclusions about what is going on in these cases. So far, common factors are Android 7 and specific Samsung devices (S6 and S7) but I believe that there must be some other app or setting that must be in play as well (since otherwise I would expect that we would have received many more instances of this issue than we have done...)
Frustratingly, getting the logs for these things is not straightforward (they don't get sent to us automatically), but if any guys who have suffered this "the app has stopped working" issue also happen to have the android development tools installed on their PC and can extract this data, it would be useful. Beyond that, the only other thing that would really help us narrow down the issue would be if we could borrow an affected device to run some tests, so if you have an affected device that you can spare to send us, please use the regular web contact form to arrange that.
|
|
|
|
|
deanpearcy
|
|
|
Group: Forum Members
Posts: 6,
Visits: 5
|
I am having the same issues on a GS7 edge. The app just will not open and it gives no useful reason why, other than "the app has stopped working"!
I am running android 7.0 which I believe updated recently and I have no idea if the SD app worked immediately after the update as I didn't try it. All I know is, it used to work and now it doesn't. I have uninstalled and reinstalled the software, today, so I know it's the most current version.
|
|
|
|
|
cocoroman
|
|
|
Group: Forum Members
Posts: 70,
Visits: 116
|
+x+xKunkrab, are you posting in this thread because you believe you are encountering the same issue as the OP? Cocoroman, I'm sorry but I have no idea what Samsung Easy Mode is, or what effects it has on your device's ability to perform the standard functions SkyDemon asks of it. The best thing is to stay in touch with customer support because they will know if anybody else is reporting the same sort of problem. Kunkrab above is not, I don't think. Yes, it is an immediate crash that makes the app unusable. The common factor seems to be the latest Android release. I don't know what Easy Mode is either. I tried setting battery saving mode to no avail. Will contact support. Easy mode is on Display setup; which will offer you Bigger and easier way of accessing The samsung galaxy S6. other wise you'll have the Standard mode, which is default mode. Today (18 June 2017) I have tried to installed SD, it is same problem again, it's just not working on easy mode. The new update Android 7.0, has a lot's of bugs. And the story goes ..
|
|
|
|
|
Kunkrab
|
|
|
Group: Forum Members
Posts: 3,
Visits: 0
|
+xKunkrab, are you posting in this thread because you believe you are encountering the same issue as the OP? Cocoroman, I'm sorry but I have no idea what Samsung Easy Mode is, or what effects it has on your device's ability to perform the standard functions SkyDemon asks of it. The best thing is to stay in touch with customer support because they will know if anybody else is reporting the same sort of problem. Kunkrab above is not, I don't think. Yes, it is an immediate crash that makes the app unusable. The common factor seems to be the latest Android release. I don't know what Easy Mode is either. I tried setting battery saving mode to no avail. Will contact support.
|
|
|
|
|
Tim Dawson
|
|
|
Group: Forum Members
Posts: 8.1K,
Visits: 9.4K
|
Kunkrab, are you posting in this thread because you believe you are encountering the same issue as the OP?
Cocoroman, I'm sorry but I have no idea what Samsung Easy Mode is, or what effects it has on your device's ability to perform the standard functions SkyDemon asks of it. The best thing is to stay in touch with customer support because they will know if anybody else is reporting the same sort of problem. Kunkrab above is not, I don't think.
|
|
|
|
|
Kunkrab
|
|
|
Group: Forum Members
Posts: 3,
Visits: 0
|
Here's what happens to me: Google Pixel, latest OS, 7.1.2, latest SkyDemon (no idea on how to find the version number when no charts are installed). Keeps crashing on initial chart download . Attached a adb Android debugger, some GL stuff failing, maybe it helps. 05-28 08:48:23.648 15567 15567 D RcsService: Never provisioned and provisioning is not allowed, skipped config update request
05-28 08:48:23.709 8298 8298 D BugleThrottledAction: CountryCodeDetectorAction already scheduled in 101511ms, not scheduling it again.
05-28 08:48:23.709 8298 8298 D BugleThrottledAction: CountryCodeDetectorAction already scheduled in 101500ms, not scheduling it again.
05-28 08:48:24.220 30829 30744 W GmsLocationProvider: Error removing location updates: 16
05-28 08:48:25.663 30938 31005 W Adreno-GSL: <sharedmem_gpuobj_alloc:1923>: sharedmem_gpumem_alloc: mmap failed errno 12 Out of memory
05-28 08:48:25.666 30938 31005 E Adreno-GSL: <gsl_memory_alloc_pure:2115>: GSL MEM ERROR: kgsl_sharedmem_alloc ioctl failed.
05-28 08:48:25.667 30938 31005 W Adreno-GSL: <sharedmem_gpuobj_alloc:1923>: sharedmem_gpumem_alloc: mmap failed errno 12 Out of memory
05-28 08:48:25.670 30938 31005 E Adreno-GSL: <gsl_memory_alloc_pure:2115>: GSL MEM ERROR: kgsl_sharedmem_alloc ioctl failed.
05-28 08:48:25.672 30938 31005 W Adreno-GSL: <sharedmem_gpuobj_alloc:1923>: sharedmem_gpumem_alloc: mmap failed errno 12 Out of memory
05-28 08:48:25.675 30938 31005 E Adreno-GSL: <gsl_memory_alloc_pure:2115>: GSL MEM ERROR: kgsl_sharedmem_alloc ioctl failed.
05-28 08:48:25.676 30938 31005 W Adreno-GSL: <sharedmem_gpuobj_alloc:1923>: sharedmem_gpumem_alloc: mmap failed errno 12 Out of memory
05-28 08:48:25.680 30938 31005 E Adreno-GSL: <gsl_memory_alloc_pure:2115>: GSL MEM ERROR: kgsl_sharedmem_alloc ioctl failed.
05-28 08:48:25.680 30938 31005 W Adreno-GSL: <sharedmem_gpuobj_alloc:1923>: sharedmem_gpumem_alloc: mmap failed errno 12 Out of memory
05-28 08:48:25.684 30938 31005 E Adreno-GSL: <gsl_memory_alloc_pure:2115>: GSL MEM ERROR: kgsl_sharedmem_alloc ioctl failed.
05-28 08:48:25.685 30938 31005 W Adreno-GSL: <sharedmem_gpuobj_alloc:1923>: sharedmem_gpumem_alloc: mmap failed errno 12 Out of memory
05-28 08:48:25.688 30938 31005 E Adreno-GSL: <gsl_memory_alloc_pure:2115>: GSL MEM ERROR: kgsl_sharedmem_alloc ioctl failed.
05-28 08:48:25.690 30938 31005 E OpenGLRenderer: GL error: Out of memory!
05-28 08:48:25.690 30938 31005 F OpenGLRenderer: GL errors! frameworks/base/libs/hwui/renderthread/CanvasContext.cpp:550
05-28 08:48:25.690 30938 31005 F libc : Fatal signal 6 (SIGABRT), code -6 in tid 31005 (RenderThread)
05-28 08:48:25.691 568 568 W : debuggerd: handling request: pid=30938 uid=10134 gid=10134 tid=31005
05-28 08:48:25.773 31311 31311 F DEBUG : *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
05-28 08:48:25.773 31311 31311 F DEBUG : Build fingerprint: 'google/sailfish/sailfish:7.1.2/N2G47T/3896053:user/release-keys'
05-28 08:48:25.773 31311 31311 F DEBUG : Revision: '0'
05-28 08:48:25.773 31311 31311 F DEBUG : ABI: 'arm'
05-28 08:48:25.774 31311 31311 F DEBUG : pid: 30938, tid: 31005, name: RenderThread >>> aero.skydemon.skydemonandroid <<<
05-28 08:48:25.774 31311 31311 F DEBUG : signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr --------
05-28 08:48:25.780 31311 31311 F DEBUG : Abort message: 'GL errors! frameworks/base/libs/hwui/renderthread/CanvasContext.cpp:550'
05-28 08:48:25.780 31311 31311 F DEBUG : r0 00000000 r1 0000791d r2 00000006 r3 00000008
05-28 08:48:25.780 31311 31311 F DEBUG : r4 d2f7f978 r5 00000006 r6 d2f7f920 r7 0000010c
05-28 08:48:25.780 31311 31311 F DEBUG : r8 cdb4b780 r9 00000000 sl e954b87c fp e954b878
05-28 08:48:25.780 31311 31311 F DEBUG : ip 0000000c sp d2f7ef38 lr f2e595c7 pc f2e5be30 cpsr 600f0010
05-28 08:48:25.797 31311 31311 F DEBUG :
05-28 08:48:25.797 31311 31311 F DEBUG : backtrace:
05-28 08:48:25.797 31311 31311 F DEBUG : #00 pc 00049e30 /system/lib/libc.so (tgkill+12)
05-28 08:48:25.797 31311 31311 F DEBUG : #01 pc 000475c3 /system/lib/libc.so (pthread_kill+34)
05-28 08:48:25.797 31311 31311 F DEBUG : #02 pc 0001d635 /system/lib/libc.so (raise+10)
05-28 08:48:25.797 31311 31311 F DEBUG : #03 pc 00019181 /system/lib/libc.so (__libc_android_abort+34)
05-28 08:48:25.798 31311 31311 F DEBUG : #04 pc 00017048 /system/lib/libc.so (abort+4)
05-28 08:48:25.798 31311 31311 F DEBUG : #05 pc 0000c3f7 /system/lib/libcutils.so (__android_log_assert+114)
05-28 08:48:25.798 31311 31311 F DEBUG : #06 pc 000240a5 /system/lib/libhwui.so
05-28 08:48:25.798 31311 31311 F DEBUG : #07 pc 00025ab3 /system/lib/libhwui.so
05-28 08:48:25.798 31311 31311 F DEBUG : #08 pc 000290a9 /system/lib/libhwui.so (_ZN7android10uirenderer12renderthread12RenderThread10threadLoopEv+80)
05-28 08:48:25.798 31311 31311 F DEBUG : #09 pc 0000e325 /system/lib/libutils.so (_ZN7android6Thread11_threadLoopEPv+144)
05-28 08:48:25.798 31311 31311 F DEBUG : #10 pc 00067f29 /system/lib/libandroid_runtime.so (_ZN7android14AndroidRuntime15javaThreadShellEPv+80)
05-28 08:48:25.798 31311 31311 F DEBUG : #11 pc 00047093 /system/lib/libc.so (_ZL15__pthread_startPv+22)
05-28 08:48:25.798 31311 31311 F DEBUG : #12 pc 00019bdd /system/lib/libc.so (__start_thread+6)
05-28 08:48:25.843 1212 1492 I nanohub : osLog: [BMI160] accSetRate: rate=51200, latency=-256, state=4
05-28 08:48:25.845 1212 1492 D ActivityRecognitionHAL: OnActivityEvent sensorIndex = 33, eventIndex = 194, whenNs = 2250410966966107
05-28 08:48:25.845 1212 1492 D ActivityRecognitionHAL: Publishing event - activity_handle: 0, event_type: 0, timestamp: 2250410966966107
05-28 08:48:25.884 1212 1492 I nanohub : osLog: [BMI160] accSetRate: rate=51200, latency=-256, state=3
05-28 08:48:25.884 1212 1492 D ActivityRecognitionHAL: OnActivityEvent sensorIndex = 40, eventIndex = 195, whenNs = 2250410966966107
05-28 08:48:25.884 1212 1492 D ActivityRecognitionHAL: Publishing event - activity_handle: 4, event_type: 0, timestamp: 2250410966966107
|
|
|
|
|
cocoroman
|
|
|
Group: Forum Members
Posts: 70,
Visits: 116
|
+xAlso, there is no need to create three threads when one will do. Hi Tim, first of all, wish you a great Holiday, sorry to be sound a little angry about it. The reason I have made 3 thread is, as the first wasn't working with the new update and suddenly I have found out that; it was because of Easy Mode problem and I wanted warn all our members in case. On second thread, I thought, yes it is working on Standard Mode, again I have written on the forum. And the 3. one reconfirming that it is not Easy or Standard mode, it is just not working with the new Update. And again I have warned our members, thats why. BTW, you have seen all 3 threads I guess, because you have answered to some members, to other threads on the same dates. But not to me. fair enough..
|
|
|
|
|
T67M
|
|
|
Group: Forum Members
Posts: 206,
Visits: 3.2K
|
I can also add that I'm using SkyDemon with Android 7 and I haven't experienced any problems at all - but I'm using a Google Pixel XL. The problems on a Samsung phone could be modifications which Samsung have made to Android, or it could be another app you have installed which I don't use. My first suspicion would be things like Samsung Easy mode though as that probably results in some quite deep changes under the hood.
|
|
|
|
|
Tim Dawson
|
|
|
Group: Forum Members
Posts: 8.1K,
Visits: 9.4K
|
Also, there is no need to create three threads when one will do.
|
|
|
|